[Veeam Connector] - Updated the authentication type - #14793
Open
dhanunjaya1054 wants to merge 1 commit into
Open
[Veeam Connector] - Updated the authentication type#14793dhanunjaya1054 wants to merge 1 commit into
dhanunjaya1054 wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the Veeam connector to use OAuth2 password-grant authentication (instead of bearer token/API key) and refresh tokens automatically, along with corresponding metadata/version bumps and user-facing setup instructions.
Changes:
- Switched RestApiPoller authentication from
APIKeytoOAuth2(password grant) for VBR and Veeam ONE pollers. - Updated connector setup UX copy/fields from “Bearer Token” to username/password (+ optional client credentials).
- Bumped solution version to
3.2.0in solution metadata and solution data.
Reviewed changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| Solutions/Veeam/SolutionMetadata.json | Version bump to 3.2.0 and JSON formatting changes. |
| Solutions/Veeam/Data/Solution_Veeam.json | Version bump to 3.2.0 in solution data. |
| Solutions/Veeam/Data Connectors/Veeam_CCF/Veeam_PollerConfig.json | Migrates poller auth to OAuth2 password grant and adds token endpoints/credentials. |
| Solutions/Veeam/Data Connectors/Veeam_CCF/Veeam_ConnectorDefinition.json | Updates UI instructions/fields to collect OAuth2 credentials instead of bearer tokens. |
Comment on lines
+10
to
+19
| "type": "OAuth2", | ||
| "GrantType": "password", | ||
| "TokenEndpoint": "[[concat(parameters('veeamApiUrl'),'/api/oauth2/token')]", | ||
| "TokenEndpointHeaders": { | ||
| "x-api-version": "1.3-rev1" | ||
| }, | ||
| "ClientId": "[[parameters('veeamClientId')]", | ||
| "ClientSecret": "[[parameters('veeamClientSecret')]", | ||
| "UserName": "[[parameters('veeamUsername')]", | ||
| "Password": "[[parameters('veeamPassword')]" |
| { | ||
| "title": "3. Veeam API Configuration", | ||
| "description": "Configure Veeam API credentials for all Veeam services (Malware Events, Security Analyzer, and Authorization Events).", | ||
| "description": "Configure Veeam Backup & Replication credentials for all VBR services (Malware Events, Security Analyzer, Authorization Events and Sessions). Sentinel authenticates via OAuth2 password grant and renews the token automatically.", |
Comment on lines
+16
to
+17
| "ClientId": "[[parameters('veeamClientId')]", | ||
| "ClientSecret": "[[parameters('veeamClientSecret')]", |
Comment on lines
+196
to
197
| "Version": "3.2.0", | ||
| "DataConnectorCCFVersion": "3.1.0", |
| "type": "Markdown", | ||
| "parameters": { | ||
| "content": "#### 3.1 Obtain Veeam API Access Token\n1. Access your Veeam Backup & Replication management console\n2. Navigate to the REST API settings or authentication section\n3. Generate or obtain a Bearer token for API access\n4. Ensure the token has appropriate permissions for:\n - Malware Detection API (v1.3-rev1)\n - Security & Compliance Analyzer API (v1.3-rev1)\n - Authorization Events API (v1.3-rev1)\n - Sessions API (v1.3-rev1)\n5. Note the API base URL (typically https://your-veeam-server.com:9419)\n6. This token will be used for both on-premises and CDN-hosted APIs" | ||
| "content": "#### 3.1 Configure Veeam Backup & Replication credentials\n1. Access your Veeam Backup & Replication management console.\n2. Use (or create) a user account that has REST API access with permissions for the Malware Detection, Security & Compliance Analyzer, Authorization Events and Sessions APIs (v1.3-rev1).\n3. Note the API base URL (typically https://your-veeam-server.com:9419).\n4. Microsoft Sentinel signs in with these credentials against `/api/oauth2/token` (OAuth2 password grant) and automatically refreshes the access token, so collection no longer stops when the token expires.\n5. Client ID / Client Secret are optional - leave them blank unless your Veeam server is configured to require a registered OAuth2 client." |
|
@v-atulyadav @v-shukore |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Required items, please complete
Change(s):
Reason for Change(s):
Version Updated:
Testing Completed: